This repository has been archived by the owner on Sep 26, 2023. It is now read-only.
fix: retain user RPC timeout if set via withTimeout #1324
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a Callable has
RetrySettings
and the calculated RPC Timeout for an attempt is less than the constant, RPC timeout provided by the user viaApiCallContext.withTimeout
, the attempt settings will win. This is not caller friendly.This PR changes
AttemptCallable
, used for Unary RPCs, only attempts to set theApiCallContext.withTimeout
when it is not already set by the caller.This was fixed for ServerStreaming RPCs in #1155
Addresses commentary in #1144.